Skip to content

Add security warning about publicly exposed PHP-FPM - #5263

Merged
lacatoire merged 4 commits into
php:masterfrom
lacatoire:fix/fpm-security-warning
Sep 2, 2026
Merged

Add security warning about publicly exposed PHP-FPM#5263
lacatoire merged 4 commits into
php:masterfrom
lacatoire:fix/fpm-security-warning

Conversation

@lacatoire

Copy link
Copy Markdown
Member

Summary

  • Add a prominent <warning> block to the FPM main page (install/fpm/index.xml) about the
    risk of exposing PHP-FPM to untrusted networks (arbitrary code execution)
  • Cover Unix sockets vs TCP sockets, listen.allowed_clients, and Docker/container best
    practices
  • Add a matching warning on the listen directive in install/fpm/configuration.xml

Fixes #3984

@lacatoire lacatoire closed this Mar 2, 2026
@lacatoire lacatoire reopened this Aug 21, 2026
@lacatoire
lacatoire force-pushed the fix/fpm-security-warning branch 2 times, most recently from 520a3af to 58b3c13 Compare August 21, 2026 10:00
@lacatoire
lacatoire force-pushed the fix/fpm-security-warning branch from 58b3c13 to 6d230ce Compare August 21, 2026 10:04
fastcgi_abort_request() does not exist: the FPM SAPI only declares
fastcgi_finish_request(). The <simpara> conversion the style check
requires is kept.

The chapter warning now states the mechanism instead of asserting the
risk, and moves after the feature list so it no longer splits the
sentence introducing it. The listen warning carries the operational
detail, names listen.owner and the BSD caveat, and no longer repeats
the chapter.
@lacatoire
lacatoire merged commit 7efe863 into php:master Sep 2, 2026
2 checks passed
@lacatoire
lacatoire deleted the fix/fpm-security-warning branch September 2, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a "big red warning" about making sure php-fpm is not publicly exposed

1 participant